-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUGFIX] Fix siteLanguage("locale")
TypoScript condition example
#1449
Conversation
Tests should run after rebasing, failures where not related to this PR |
I synced the changes from upstream to my fork in Github. |
Hello @cundd I have tested that behavior. In TYPO3 core I found a Charset normalizer which converts all underscores to dashes. Thank you for your patch. I have just merged it. Stefan |
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-13.4 13.4
# Navigate to the new working tree
cd .worktrees/backport-13.4
# Create a new branch
git switch --create backport-1449-to-13.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 9f106d7d3f357d646d26891c97834cb174178b10,4dfbc334b71bfcc5fa90f5ea014cad08cb23a21d
# Push it to GitHub
git push --set-upstream origin backport-1449-to-13.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-13.4 Then, create a pull request where the |
…1449) (#1502) Co-authored-by: Daniel Corn <[email protected]>
The current example for the
siteLanguage
condition does not seem to be working. If I understand the code correctly, the locale string will be normalized to use dashes (e.g.fr-CH
) as separator instead of an underscore (fr_CH
) (see Locale.php.The output of "locale" in
<f:debug>{siteLanguage}</f:debug>
is also a bit misleading as it uses theposixFormatted
version instead of the one used in the TypoScript condition.Please check this proposed change carefully, as I may not understand the whole picture and/or some things depend on the actual hosting environment.
Successor of PR #1436